Device identifier dependent operation processing of packet based data communication

ABSTRACT

Identifier dependent operation processing of packet based data communication is provided. A natural language processor component can parse an input audio signal to identify a request and a trigger keyword. A content selector component can select, based on the request or trigger keyword, a content item. A link generation component can determine whether the client computing device has an account or a record in a database associated with the service provider device. In the absence of the record or account, the link generation device generates and sends a virtual identifier to the service provider device with instructions to generate an account in the database using the virtual identifier. Once the account is created, the service provider device can communicate with the client computing device.

BACKGROUND

Excessive network transmissions, packet-based or otherwise, of network traffic data between computing devices can prevent a computing device from properly processing the network traffic data, completing an operation related to the network traffic data, or timely responding to the network traffic data. The excessive network transmissions of network traffic data can also complicate data routing or degrade the quality of the response if the responding computing device is at or above its processing capacity, which may result in inefficient bandwidth utilization. The control of network transmissions corresponding to content item objects can be complicated by the large number of content item objects that can initiate network transmissions of network traffic data between computing devices.

SUMMARY

At least one aspect is directed to a system to provide identifier dependent operation processing of packet based data communication. The system includes a natural language processor component executed by a data processing system to receive, via an interface of the data processing system, data packets comprising an input audio signal detected by a sensor of a client computing device having a device identifier. The natural language processor component parses the input audio signal to identify a request and a trigger keyword corresponding to the request. The system further includes a content selector component executed by the data processing system to receive the trigger keyword identified by the natural language processor and to select, based on the trigger keyword, a content item via a real-time content selection process. The system also includes a link generation component to perform a lookup of a device identifier of the client computing device in a database storing account identifiers established for a service provider device corresponding to the content item. The system further includes the link generation component to determine an absence of the device identifier of the client computing device in the database based on a null command received in response to the lookup. The system further includes the link generation component to generate, a virtual identifier for the client device and link the virtual identifier to the device identifier, and to route data packets that carry, in a payload section, the virtual identifier to service provider device to cause the service provider device to establish an account for the client computing device based on the virtual identifier. The system also includes the data processing system to receive, from the service provider device, an indication that the service provider device established the account using the virtual identifier, and performed an operation with the client computing device.

At least one aspect is directed to a method to invoke actions for identifier dependent operation processing of packet data communication between a client computing device and a service provider device using a data processing system. The method includes receiving, by a natural language processor component executed by the data processing system, from the client computing device an audio signal corresponding to a voice command. The method further includes processing, by the natural language processor component, the audio signal to identify a request for a service and a trigger keyword corresponding to the request. The method also includes selecting, by a content selector component executed by the data processing system, based on the keyword, a content item corresponding to the service provider device communicably coupled to the data processing system. The method additionally includes determining, by a link generation component executed by the data processing system, an absence of a database record corresponding to a client computing device identifier associated with the client computing device in a database associated with the service provider device. The method further includes generating, by the link generation component responsive to determining the absence, a virtual identifier associated with the client computing device, the virtual identifier being distinct from the client computing device identifier. The method also includes sending, by the link generation component, the virtual identifier to the service provider device. The method additionally includes receiving, by the link generation component, a first message from the service provider device indicating establishment of a database record corresponding to the virtual identifier.

At least one aspect is directed to a computer readable storage medium storing instructions that when executed by one or more data processors, cause the one or more data processors to perform operations for identifier dependent operation processing of packet based data communication between a client computing device and a service provider device. The operations can receive, by a natural language processor component executed by the data processing system, from the client computing device, an audio signal corresponding to a voice command. The operations can process, by the natural language processor component, the audio signal to identify a request for a service and a trigger keyword corresponding to the request. The operations can select by a content selector component executed by the data processing system, based on the keyword, a content item corresponding to the service provider device communicably coupled to the data processing system. The operations can determine by a link generation component executed by the data processing system, an absence of a database record corresponding to a client computing device identifier associated with the client computing device in a database associated with the service provider device. The operations can generate by the link generation component responsive to determining the absence, a virtual identifier associated with the client computing device, the virtual identifier being distinct from the client computing device identifier. The operations can send by the link generation component, the virtual identifier to the service provider device. The operations can receive by the link generation component, a first message from the service provider device indicating establishment of a database record corresponding to the virtual identifier.

These and other aspects and implementations are discussed in detail below. The foregoing information and the following detailed description include illustrative examples of various aspects and implementations, and provide an overview or framework for understanding the nature and character of the claimed aspects and implementations. The drawings provide illustration and a further understanding of the various aspects and implementations, and are incorporated in and constitute a part of this specification.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are not intended to be drawn to scale. Like reference numbers and designations in the various drawings indicate like elements. For purposes of clarity, not every component may be labeled in every drawing. In the drawings:

FIG. 1 depicts a system to optimize processing of sequence dependent operations in a voice activated computer network environment;

FIGS. 2A-2C depict representations of data structures used by a data processing system to send information to a service provider device.

FIGS. 3 depicts a functional diagram of a thread including sequence dependent actions;

FIG. 4 depicts method to invoke actions for establishing communications between a client computing device and a service provider device in a voice activated data packet based computer network environment; and

FIG. 5 is a block diagram illustrating a general architecture for a computer system that may be employed to implement elements of the systems and methods described and illustrated herein.

DETAILED DESCRIPTION

Following below are more detailed descriptions of various concepts related to, and implementations of, methods, apparatuses, and systems to optimize processing of sequence dependent operations in a voice activated computer network environment. The various concepts introduced above and discussed in greater detail below may be implemented in any of numerous ways.

Systems and methods of the present disclosure relate generally to a data processing system that improves the efficiency, reliability, and operability of data packet transmissions between a client computing device and a service provider device in a voice activated computer network environment. For example, the data processing system can facilitate a creation of records or accounts associated with the client computing device in a database of the service provider device such that the service provider device can communicate with, and provide requested services to, the client computing device. The creation of records or accounts on behalf of the client computing device also improves efficiency and reduces resource use by avoiding the need for communication between the service provider device and the client computing device to establish a record or account prior to providing a requested service. Data packets or other protocol based signals corresponding to the selected operations can be routed through a computer network between multiple computing devices. The data processing system can receive audio signals representing user commands or requests, and identify specific requests and keywords. Based on the requests or keywords, the data processing system can present the client computing device with content items that represent alternative service options. The data processing system can determine whether the computing device has selected the alternative service option and further determine whether the service provider device associated with the alternative service option includes a record or an account associated with the client computing device. The absence of a record or an account may prevent the service provider device from communicating with, and providing the requested services to, the client computing device.

To improve the efficiency, reliability, and operability of data packet transmissions between a client computing device and a service provider device in a voice activated computer network environment, systems and methods described herein can include a data processing system that, upon detecting an absence of a record or an account associated with the client computing device with the service provider device, can establish a data packet based communication session on behalf of the client computing device and instruct the service provider device to create an account without any intervention from the client computing device. The data processing system can generate virtual identifiers (or virtual tokens), representing the client computing device, that can be sent to the service provider devices to generate records or accounts. Once the record or the account for the client computing device has been created, the service provider is able to establish secure communications with the client computing device and provide the requested service.

FIG. 1 depicts an example system 100 to optimize processing of sequence dependent operations in a voice activated data packet (or other protocol) based computer network environment. The system 100 can include at least one data processing system 105. The data processing system 105 can include at least one server having at least one processor. For example, the data processing system 105 can include a plurality of servers located in at least one data center or server farm. The data processing system 105 can determine, from an audio input signal a request and a trigger keyword associated with the request. Based on the request and trigger keyword the data processing system 105 can determine or select a thread that includes a plurality of sequence dependent operations, and can select content items (and initiate other actions as described herein). The content items can include one or more audio files that when rendered provide an audio output or acoustic wave. The content items can include other content (e.g., text, video, or image content) in addition to audio content.

The data processing system 105 can include multiple, logically-grouped servers and facilitate distributed computing techniques. The logical group of servers may be referred to as a data center, server farm or a machine farm. The servers can be geographically dispersed. A data center or machine farm may be administered as a single entity, or the machine farm can include a plurality of machine farms. The servers within each machine farm can be heterogeneous—one or more of the servers or machines can operate according to one or more type of operating system platform. The data processing system 105 can include servers in a data center that are stored in one or more high-density rack systems, along with associated storage systems, located for example in an enterprise data center. The data processing system 105 with consolidated servers in this way can improve system manageability, data security, the physical security of the system, and system performance by locating servers and high performance storage systems on localized high performance networks. Centralization of all or some of the data processing system 105 components, including servers and storage systems, and coupling them with advanced system management tools allows more efficient use of server resources, which saves power and processing requirements and reduces bandwidth usage.

The data processing system 105 can include at least one natural language processor (NLP) component 110, at least one interface 115, at least one link generation component 120, at least one content selector component 125, at least one audio signal generator component 130, at least one direct action application programming interface (API) 135, at least one session handler component 140, and at least one data repository 145. The NLP component 110, interface 115, link generation component 120, content selector component 125, audio signal generator component 130, direct action API 135, and session handler component 140 can each include at least one processing unit, server, virtual server, circuit, engine, agent, appliance, or other logic device such as programmable logic arrays configured to communicate with the data repository 145 and with other computing devices (e.g., the client computing device 150, the content provider computing device 155, or the service provider device 160) via the at least one computer network 165. The direct action API 135 can execute a specified action to satisfy an intention of a user at the client computing device 150, as determined by the data processing system 105. Depending on the action specified in its inputs, the direct action API 135 can execute code or a dialog script that identifies the parameters required to fulfill a user request. Such code can lookup additional information, e.g., in the data repository 145, such as the name of a home automation service, or it can provide audio output for rendering at the client computing device 150 to ask the end user questions such as the intended destination of a requested taxi. The direct action API 135 can determine necessary parameters and can package the information into an action data structure, which can then be sent to another component such as the content selector component 125 or to the service provider computing device 160 to be fulfilled.

The network 165 can include computer networks such as the internet, local, wide, metro or other area networks, intranets, satellite networks, other computer networks such as voice or data mobile phone communication networks, and combinations thereof. The network 165 can include or constitute a display network, e.g., a subset of information resources available on the internet that are associated with a content placement or search engine results system, or that are eligible to include third party content items as part of a content item placement campaign. The network 165 can be used by the data processing system 105 to access information resources such as web pages, web sites, domain names, or uniform resource locators that can be presented, output, rendered, or displayed by the client computing device 150. For example, via the network 165 a user of the client computing device 150 can access information or data provided by the content provider computing device 155 or the service provider device 160.

The network 165 can include, for example a point-to-point network, a broadcast network, a wide area network, a local area network, a telecommunications network, a data communication network, a computer network, an ATM (Asynchronous Transfer Mode) network, a SONET (Synchronous Optical Network) network, a SDH (Synchronous Digital Hierarchy) network, a wireless network or a wireline network, and combinations thereof. The network 165 can include a wireless link, such as an infrared channel or satellite band. The topology of the network 165 may include a bus, star, or ring network topology. The network 165 can include mobile telephone networks using any protocol or protocols used to communicate among mobile devices, including advanced mobile phone protocol (“AMPS”), time division multiple access (“TDMA”), code-division multiple access (“CDMA”), global system for mobile communication (“GSM”), general packet radio services (“GPRS”) or universal mobile telecommunications system (“UMTS”). Different types of data may be transmitted via different protocols, or the same types of data may be transmitted via different protocols.

The client computing device 150, the content provider computing device 155, and the service provider device 160 can each include at least one logic device such as a computing device having a processor to communicate with each other or with the data processing system 105 via the network 165. The client computing device 150, the content provider computing device 155, and the service provider device 160 can each include at least one server, processor or memory, or a plurality of computation resources or servers located in at least one data center. The client computing device 150, the content provider computing device 155, and the service provider device 160 can each include at least one computing device such as a desktop computer, laptop, tablet, personal digital assistant, smartphone, portable computer, thin client computer, virtual server, or other computing device.

The client computing device 150 can include at least one sensor 151, at least one transducer 152, at least one audio driver 153, and at least one speaker 154. The sensor 151 can include a microphone or audio input sensor. The transducer 152 can convert the audio input into an electronic signal. The audio driver 153 can include a script or program executed by one or more processors of the client computing device 150 to control the sensor 151, the transducer 152 or the audio driver 153, among other components of the client computing device 150 to process audio input or provide audio output. The speaker 154 can transmit the audio output signal. The computing device 150 may or may not include a display; for example, the computing device may include limited types of user interfaces, such as a microphone and speaker. In some cases, the primary user interface of the computing device 150 may be a microphone and speaker.

The client computing device 150 can be associated with an end user that enters voice queries as audio input into the client computing device 150 (via the sensor 151) and receives audio output in the form of a computer generated voice that can be provided from the data processing system 105 (or the content provider computing device 155 or the service provider device 160) to the client computing device 150, output from the speaker 154. The computer generated voice can include recordings from a real person or computer generated language.

The content provider computing device 155 can provide audio based content items for display by the client computing device 150 as an audio output content item. The content item can include an offer for a good or service, such as a voice based message that states: “Would you like me to order you a taxi?” For example, the content provider computing device 155 can include memory to store a series of audio content items that can be provided in response to a voice based query. The content provider computing device 155 can also provide audio based content items (or other content items) to the data processing system 105 where they can be stored in the data repository 145. The data processing system 105 can select the audio content items and provide (or instruct the content provider computing device 155 to provide) the audio content items to the client computing device 150. The audio based content items can be exclusively audio or can be combined with text, image, or video data.

The service provider device 160 can include at least one service provider natural language processor (NLP) component 161 and at least one service provider interface 162. The service provider NLP component 161 (or other components such as a direct action API of the service provider device 160) can engage with the client computing device 150 (via the data processing system 105 or bypassing the data processing system 105) to create a back-and-forth real-time voice or audio based conversation (e.g., a session) between the client computing device 150 and the service provider device 160. For example, the service provider interface 162 can receive or provide data messages to the direct action API 135 of the data processing system 105. The service provider device 160 and the content provider computing device 155 can be associated with the same entity. For example, the content provider computing device 155 can create, store, or make available content items for a car sharing service, and the service provider device 160 can establish a session with the client computing device 150 to arrange for a delivery of a taxi or car of the car share service to pick up the end user of the client computing device 150. The data processing system 105, via the direct action API 135, the NLP component 110 or other components can also establish the session with the client computing device 150, including or bypassing the service provider device 160, to arrange for example for a delivery of a taxi or car of the car share service.

The data repository 145 can include one or more local or distributed databases, and can include a database management system. The data repository 145 can include computer data storage or memory and can store one or more parameters 146, one or more identifiers 147, content data 148, or templates 149 among other data. The parameters 146, identifiers 147, and templates 149 can include information such as rules about a voice based session between the client computing device 150 and the data processing system 105 (or the service provider device 160). The identifiers 147, in particular, can include data associated with an identity of the client computing device 150 or an identity of a user of the client computing device 150. The identifiers 147 also can include one or more unique identifiers (also referred to herein as virtual identifiers or virtual tokens) generated by the data processing system 105 and associated with the client computing device 150 or the user of the client computing device 150. The content data 148 can include content items for audio output or associated metadata, as well as input audio messages that can be part of one or more communication sessions with the client computing device 150.

The data processing system 105 can include an application, script or program installed at the client computing device 150, such as an app to communicate input audio signals to the interface 115 of the data processing system 105 and to drive components of the client computing device 150 to render output audio signals. The data processing system 105 can receive data packets or other signal that includes or identifies an audio input signal. For example, the data processing system 105 can execute or run the NLP component 110 to receive the audio input signal. The NLP component 110 can convert the received audio input signal into recognized text by comparing the audio input signal against a stored, representative set of audio waveforms and choosing the ones that are a closest match. The representative waveforms are generated across a large set of users, and may be augmented with speech samples from the user. After the received audio input signal is converted into recognized text, the NLP component 110 matches the text to words that are associated, for example, via training across users or through manual specification, with actions or commands that the data processing system 105 can serve. The audio input signal can be detected by the sensor 151 (e.g., a microphone) of the client computing device 150. Via the transducer 152, the audio driver 153, or other components the client computing device 150 can provide the audio input signal to the data processing system 105 (e.g., via the network 165) where it can be received (e.g., by the interface 115) and provided to the NLP component 110 or stored in the data repository 145 as content data 148.

The NLP component 110 can obtain the input audio signal. From the input audio signal, the NLP component 110 can identify at least one request or at least one trigger keyword corresponding to the request. The request can indicate intent or subject matter of the input audio signal. The trigger keyword can indicate a type of action likely to be taken. For example, the NLP component 110 can parse the input audio signal to identify at least one request to leave home for the evening to attend dinner and a movie. The trigger keyword can include at least one word, phrase, root or partial word, or derivative indicating an action to be taken. For example, one or more of trigger keywords, such as “ride,” “cab,” or “taxi” identified from the input audio signal can indicate a need for transport. In another example, one or more keywords such as “go,” or “to go to,” identified from the input audio signal also may indicate a need for transport. In this example, the input audio signal (or the identified request) does not directly express an intent for transport, however the trigger keyword indicates that transport is an ancillary action to at least one other action that is indicated by the request.

The data processing system 105 can determine, based on the request or the trigger keyword, at least one thread associated with the input audio signal. The thread can indicate a set of sequence dependent operations, such as a series of actions. The thread can include any two or more actions, such as a first action, a second action, and a third action. For example, the input audio signal “OK, I would like to go to go dinner and then a movie tonight” can include at least one request indicating an interest to attend dinner and a movie, and at least one trigger keyword, e.g., “go” indicating a need for transportation. The data processing system 105 can identify a thread with at least three actions, such as a dinner action (first action), a movie action (second action), and a transportation home action (third action). In this example, from the request or the trigger keyword the data processing system 105 predicts, estimates, or otherwise determine the three actions. The thread can include other actions, such as an initial transport to dinner action.

The content selector component 125 can obtain indications of any of the actions of the thread. For example, the content selector component 125 can receive an indication of the third (or any other) action identified by the data processing system. The content selector component 125 can obtain this information from the data repository 145, where it can be stored as part of the content data 148. The indication of the third action can inform the content selector component 125 of a need for transportation from the location of the movie theater to a location as determined or indicated by the client computing device 150, such as a ride to an end destination.

From the information received by the content selector component 125, the content selector component 125 can identify at least one content item. The content item can be responsive or related to the third action. For example, the content item can include an audio message offering services of a car share company, responsive to the third action that indicates a transportation need. The content selector component 125 can query the data repository 145 to select or otherwise identify the content item, e.g., from the content data 148. The content selector component 125 can also select the content item from the content provider computing device 155. For example responsive to a query received from the data processing system 105, the content provider computing device 155 can provide a content item to the data processing system 105 (or component thereof) for eventual output by the client computing device 150. The content item can be associated with a ride service to which the user has already subscribed. For example, the content item can be associated with the user's preferred ride service.

The content selector component 125 can select additional content items related to the third action. For example, the content item can include an audio message offering services of a ride service that can be offered as an alternative to the preferred ride service or a previously selected ride service for the client computing device 150. The alternative ride service can be offered to the user based on a comparison with one or more aspects of the ride service selected by the user. For example, if the fare offered by the alternative ride service is less than the ride service selected by the user, the content selector component 125 can present to the user with an option to select a cheaper alternative ride service. Other ride service aspects such as trip time, type of vehicle, and driver ratings, can also be considered. In some instances, the content selector component 125 can select a content item associated with the alternative ride service and present the content item to the user of the client computing device 150 without comparing any aspects of the two ride services.

As mentioned above, the content selector component 125, in addition to querying the data repository 145, can also communicate with the content provider device 155 to identify one or more content items. For example, the content selector component 125, upon receiving an indication of the third action associated with transportation, can communicate with the content provider device 155 to determine whether any alternative ride services are available. In response, the content selector component 125 can receive on or more content items associated with available alternative ride services. In its communication with the content provider device 155, the content selector component 125 can also include information about aspects of the transportation requested by the user to allow the content provider device 155 to provide an appropriate content item that can serve as an alternative to the ride service presented to the user. For example, the content selector component 125 can send information such as ride start address, ride destination address, requested time, number of passengers, and type of ride (e.g., economy or premium), to the content provider device 155. The content provider device 155 can use this information to determine whether one or more alternative ride services are available, and if available, send the one or more associated content items to the content selector component 125.

The audio signal generator component 130 can generate or otherwise obtain an output signal that includes the content items responsive to the third action. For example, the data processing system 105 can execute the audio signal generator component to generate or create an output signal corresponding to two or more content items, one of which can include a content item associated with, for example, the alternative ride service. The interface 115 of the data processing system 105 can transmit one or more data packets that include the output audio signal via the computer network 165 to the client computing device 150. For example, the data processing system 105 can provide the output audio signal from the data repository 145 or from the audio signal generator component 130 to the client computing device 150. The data processing system 105 can also instruct, via data packet transmissions, the content provider computing device 155 or the service provider device 160 to provide the output audio signal to the client computing device 150. The output audio signal can be obtained, generated, transformed into or transmitted as one or more data packets (or other communications protocol) from the data processing system 105 (or other computing device) to the client computing device 150.

The content selector component 125 can select the content item for the third action as part of a real-time content selection process. For example, the content item can be provided to the client computing device for transmission as audio output in a conversational manner in direct response to the input audio signal. The real-time content selection process to identify the content item and provide the content item to the client computing device 150 can occur within one minute or less from the time of the input audio signal and be considered real-time.

The output audio signal that corresponds to the content item, for example obtained or generated by the audio signal generator component 130 transmitted via the interface 115 and the computer network 165 to the client computing device 150, can cause the client computing device 150 to execute the audio driver 153 to drive the speaker 154 to generate an acoustic wave corresponding to the output audio signal. The acoustic wave can include words of or corresponding to the content item for the third action.

The acoustic wave can be output from the client computing device 150. For example, the acoustic wave can include the audio output of “Would you like to select XYZ ride service?” where “XYZ” can stand for a name or moniker for a preferred ride service. The acoustic waves associated with any additional content items can also be output from the client computing device 150. For example, the acoustic wave associated with the content item for an alternative ride service can include the audio output of “Would you like to consider an alternative ride service PQR which is $5 cheaper than the XYZ ride service?” where “PQR” can stand for a name or moniker of the alternative ride service.

The data processing system 105 can receive a response including an input audio signal from the client computing device 150. For example, the input audio signal of, for example, “OK, I would like to use PQR” From this information, the NLP component 110 identifies at least one request or at least one trigger keyword. For example, the NPL component 110 can identify a request for transportation, and a keyword “PQR” indicating that the alternative ride service PQR has been requested.

The data processing system 105 can notify the link generation component 120 to establish a link between a service provider that provides the alternative service selected by the user and the client computing device 150. The link generation component 120 can manage an establishment of a communication between the client computing device 150 and a service provider (such as the service provider device 160) associated with the service selected by the user. With reference to the example discussed above, the link generation component 120 can manage an establishment of a communication link between the client computing device 150 and the service provider device associated with the ride service “PQR,” identified by the NPL component 110 in audio signal received from the client computing device 150.

One more service provider devices, such as the service provider device 160, provide services to client computing devices, such as the client computing device 150, based on identities associated with the client computing devices. These identities can take the form of a user-name, an ID, an account number, or other parameters that can uniquely identify the client computing device 150. The service provider devices 160 can store the identities associated with various client computing devices in a client database 164 along with additional information such as conversion information, local address, user-name, password, or device address, for example. The service provider devices can use the identities and the additional information to establish and maintain communications with the client computing device, as well as for accounting or administrative purposes.

The link generation component 120 can facilitate communications between the service provider device 160 and the client computing device 150. In one example, the link generation component 120 can manage the transmission of an identity associated with the client computing device 150 to the service provider device 160, so that the service provider device 160 can verify the identity of, and if verified establish communication with, the client computing device 150. The link generation component 120 can lookup or query the data repository 145 to determine whether any identifiers identifying the client computing device 150 to the selected service exist. For example the link generation component 120 can search the identifiers 147 to determine whether any account information exists for the client computing device 150 for the selected service. The identifiers 147 can include, for example, one or more user-names or device IDs associated with the client computing device 150 and the corresponding services. If an identifier identifying the client computing device 150 to the selected service provided by the service provider device 160 exists, the link generation component 120 can send the identifier to the service provider device 160.

In some cases, the link generation component 120 performs a lookup in a database. In some cases, the link generation component 120 can cache identifiers of established or active accounts and perform a comparison to identify an absence. By caching account identifiers that are established, the data processing system may not have to perform a lookup in the service provider's database. The account identifiers can be preloaded on the data processing system so the data processing system can perform a single call to determine whether the device is associated with an active account. The data processing system can load the account identifiers (or device identifiers) based on location of the client device. With the account identifiers already loaded on the data processing system, the data processing system can determine whether the client device has an account by comparing the client device with the preloaded active account identifiers. The data processing system can determine that the client device does not have an account by not finding a matching identifier in the preloaded set of active account identifiers; or by not finding an account identifier associated with a client device identifier corresponding to the end user's client device.

The identifiers 147 may not include an identifier associated with the client computing device 150 for the service provided by the service provider device 160. For example, where the alternative service presented to the client computing device 150 is a new service that the user has never tried before, an identifier associated with the client computing device 150 for that service may not exist in the data repository 145. In some examples, while the service provider device 160 may have an identifier associated with the client computing device 150, such an identifier may not yet have been stored in the data repository 145. In such cases, the link generation component 120 can communicate with the service provider device 160 to determine the presence in the client database 164 of an identifier associated with the client computing device 150. The service provider device 160, can communicate with a client database 164, which stores client information, to determine the presence of identifiers or other data associated with the client computing device 150. Alternatively, the link generation component 120 can itself communicate with the client database 164, by a lookup or a database query operation, to determine the presence of any identifiers associated with the client computing device 150.

Once the identifier associated with the client computing device 150 is located, the link generation component 120 can send the identifier to the service provider device 160 on behalf of the client computing device 150. The link generation component 120 also can send instructions to the service provider device 160 to use the identifier to establish communication with the client computing device 150.

Where, for example, the identifier is not present in both the data repository 145 and the client database 164, the service provider device 160 may not be able to establish a communication with the client computing device. Where the service provider device 160 is able to communicate with the client computing device 150, the absence of an identifier in both the data repository and the client database 164 may need additional communication, such as queries and responses, between the service provider device 160 and the client computing device 150. For example, the service provider device 160 can request the client computing device 150 to establish an account before the service can be provided. The establishment of an account may require additional communications between the client computing device 150 and the service provider device 160 to exchange usernames, passwords, conversion information, authentication, and other information, leading to use of additional time and resources, such as bandwidth. In such cases, the link generation component 120 can facilitate the establishment of this communication by generating an account on behalf of the client computing device 150. For example, the link generation component can generate a unique virtual identifier associated with the client computing device 150. The link generation component 120 can, via the interface 115, send the virtual identifier to the service provider device 160. The virtual identifier can be communicated to the service provider device 160 using data packets (for example, in a payload section of the data packets) via the interface 115 and over the network 165. The virtual identifier can be used by the service provider device 160 to create an account or a record associated with the client computing device 150, and establish communication with the client computing device 150. In this manner, the link generation component 120 not only improves the reliability of the system by facilitating the establishment of communication between the service provider device 160 and the client computing device 150, but also improves the efficiency of the system by creating an account on behalf of the client computing device 150, thereby saving time and resources that would otherwise be utilized in communications between the service provider device 160 and the client computing device 150 to establish an account prior to providing the requested service.

The virtual identifier can be a combination of data associated with the client computing device 150. For example, the virtual identifier can include one or more of a device ID (such as a MAC ID of the client computing device 150), an Internet Protocol (IP) address of the client computing device 150, name of a user associated with the client computing device 150, a telephone number of the user, and any other data associated with the client computing device 150 which includes data associated with any user that uses the client computing device 150. The virtual identifier can be determined by processing the one or more of the above mentioned data. For example, the link generation component 120 can use a hash function to generate a virtual identifier, where an input to the hash function can be provided with one or more of the above mentioned data associated with the client computing device 150. The link generation component 120 can also use a cryptographic function (such as AES, DES, RSA, and ECC), to generate the virtual identifier, where the input to the cryptographic function can include one or more of the above mentioned data associated with the client computing device 150.

The link generation component 120 can use a digital certificate or a public key associated with the client computing device 150 as the virtual identifier. In this case, the virtual identifier can be used by the service provider device to not only authenticate the client computing device 150, but to also securely communicate with the client computing device 150 using a public key infrastructure (PM).

The link generation component 120 can send the virtual identifier to the service provider device 160. The virtual identifier can be communicated to the service provider device 160 using data packets (for example, in a payload section of the data packets) via the interface 115 and over the network 165. The service provider device 160, can use the virtual identifier to create a database entry associated with the virtual identifier. The database entry allows the service provider device 160 to create at least one record associated with the client computing device 150, and enables the service provider device 160 to identify, and thereby, communicate with the client computing device 150. The link generation component 120 can also store the virtual identifier as one of the identifiers 147 in the data repository 145. The link generation component 120 can also store a content item or an identity of the service provider device 160 in association with the virtual identifier. For example, the link generation component 120 can store the identity “PQR” of the alternative ride service selected by the user in association with the virtual identifier, or a unique identifier of the service provider device 160. This allows the link generation component 120 to determine the presence of an identifier for the client computing device 150 for the “PQR” ride service, if in the future, the client computing device 150 again selects the same ride service.

In some examples, the link generation component 120 can send additional data associated with the client computing device 150, when it sends the virtual identifier to the service provider device 160. For example, the link generation component 120 can send additional information that can facilitate the establishment of communication between the service provider device 160 and the client computing device 150. For example the link generation component 120 can send information such as home address, name of a user, and conversion information associated with the client computing device 150. The additional information also can be communicated to the service provider device 160 using data packets (for example, in a payload section of the data packets) via the interface 115 and over the network 165. This information can permit the service provider device 160 to create a database entry with information that can be sufficient to at least provide the currently requested service. Of course, the minimum amount of information associated with the client computing device 150 needed to provide the requested service may vary based on the type of service requested. In such instances, the link generation component 120 can store in the data repository 145 minimum data needed by the service provider device 160 to provide one or more services.

The link generation component 120 also can send information such as a network address of the client computing device 150 or the MAC address of the client computing device so that service provider device 160 can establish connection with the client computing device 150. The link generation component 120 can format the virtual identifier and the additional information in a data structure as per the specifications of the service provider device 160 for initiating communication or a service request.

For example, FIG. 2A shows a first data structure 200 that can be used by the link generation component 120 to send data to the service provider device 160. In particular, the first data structure 200 can be used by the link generation component 120 to send a virtual identifier to the service provider device 160 along with additional information, such as profile information of the client computing device 150, for the service provider device 160 to use to establish an account associated with the virtual identifier. The data structure 200 can improve the reliability and efficiency of data transmission between the data processing system 105 and the service provider device 160. The first data structure 200 includes fields such as Identifier, Client Computing Device Identifier, Client Computing Device Address, Conversion Information, and New Account. The Identifier field can include the virtual identifier generated by the link generation component 120 discussed above. The Client Computing Device Identifier and the Client Computing Device Address can include data that can allow the service provider device 160 to communicate with the client computing device 150, and can include a MAC address, a network address, or other identifier of the client computing device 150. The Conversion Information can include information that can allow the service provider device 160 to charge the client computing device 150 for the services rendered, and can include data such as credit card information, a code or a link to online transfer services. The New Account field can include instructions for the service provider device 160 to create a new record in the client database 164 associated with the virtual identifier included in the Identifier field. In some examples, the New Account field can include a binary message (e.g., Y/N, or 0/1.) which the service provider device 160 can interpret to mean whether to, or not, create a new record associated with the information in the Identifier field.

The link generation component 120 can send additional information to the service provider device 160 that can allow the service provider device 160 to establish connection or provide the requested service to the client computing device 150. FIG. 2B shows a second data structure 202 that can be used by the link generation component 120 to send additional information, such as service specific information, to the service provider device 160. The second data structure 202 includes fields such as Identifier, Content Item or Service, Start Address, Destination Address, Requested Time, and Conversion Information. The information included in the Identifier field can include an identifier of the client computing device 150 that is known to the service provider device 160, or a virtual identifier generated by the link generation component 120 as discussed above. The Content Item or Service field can include the specific service requested by the client computing device 150. That is, the Content Item or Service field can include a reference to the Content Item in relation to which the client computing device 150 requested service, or can include the name of the service itself. For example, the content item associated with the PQR ride service discussed above can be included, which can indicate to the service provider that the service requested is associated with the alternative content item presented to the client computing device. The Start Address and the Destination Address can include the home address and the requested destination of the requested ride service. The Requested Time field can include the pick-up time requested by client computing device 150, and the Conversion Information can include data such as credit card information, a code or a link to online transfer services.

The additional information can include information other than personal information associated with the client computing device 150. For example, the link generation component 120 can request from the client computing device 150 data such as the GPS coordinates of the client computing device 150. In cases where the client computing device 150 is a mobile device such as a smartphone, the instantaneous GPS coordinates of the client computing device 150 can be sent to the service provider device 160 so that the service provider device 160 can send the ride service based on the current location of the client computing device 150. The link generation component 120 can also request other data such as temperature, noise level, signal strength of the cell in which the client computing device 150 is currently communicating, and also send this data to the service provider device 160. FIG. 2C shows a third data structure 204 that can be used to send the above information to the service provider device 160.

The first, second, and third data structures 200, 202, and 204 can include fewer or more fields than those shown in FIGS. 2A-2C. The data processing system 105 can define the data structures in an extensible markup language (XML) for sending information to the service provider device 160. The data associated with the first, second, and third data structures 200, 202, and 204 can be communicated using data packets, for example, in the payload section of the data packets, over the network 165.

The service provider device 160 can use the virtual identifier and the additional information provided by the link generation component 120 (such as that provided in the first data structure 200) and use the information to communicate with the client computing device 150 to acquire additional information it may need to appropriately provide the requested service. For example, the service provider device 160 can use the service provider NLP component 161 to generate audio signals that query the user for additional information. The queried information can include destination address, pick-up address, requested time, and conversion information. The audio signals representative of the responses by the user at the client computing device 150 can be received by the service provider device 160 and be processed by the service provider NLP component 161 to extract the desired information. The service provider device 160 can store the extracted information in the client database 164 in association with the identifier of the client computing device 150.

The service provider device 160 can use the data processing system 105 as an intermediary to acquire the audio signals. For example, the service provider device 160 can send data packets containing text based queries in addition to a request for the data processing system 105 to convert the text based queries into audio signals and to transmit the audio signals to the client computing device 150. The NPL component 110 of the data processing system 105 can convert the text based queries into audio signals, which can be transmitted to the client computing device 150. The data processing system 105 can also receive from the client computing device 150 audio signals that include responses to the queries. The NLP component 110 can convert the audio signals into text, and transmit the converted text to the service provider device 160.

The link generation component 120 can instruct the service provider device 160 to create a temporary database record or account associated with the virtual identifier. For example, the database record associated with the virtual identifier can be deleted after the service requested by the client computing device 150 is completed. The link generation component 120 can provide a time stamp, or a duration, with the virtual identifier. The time stamp or duration can indicate that the virtual identifier is invalid after the time derived from the time stamp or the duration. The service provider device 160 can delete the database record associated with the virtual identifier if the virtual identifier is invalid.

The link generation component 120 can refrain from sending any information about the client computing device 150 or a user associated with the client computing device 150 which may compromise privacy or security. For example, the link generation component 120 can send the virtual identifier to the service provider device 160, but refrain from sending any conversion information. The conversion information can be stored at the data processing system 105, and can be used by the data processing system 105 to make conversion transactions with the service provider device 160 on behalf of the client computing device 150.

The link generation component 120 can communicate with the service provider device 160 or the client database 164 to synchronize the information stored in the data repository 145 with the data stored in the client database 164. For example, data related to accounts or records associated with the client computing device 150 can be exchanged such that the data repository 145 or the client database 164 have up to date information.

FIG. 3 depicts a representation of message flows 300 between various entities of the system 100 shown in FIG. 1. In particular, FIG. 3 depicts message flows 300 between the data processing system 105, the client computing device 150 and the service provider device 160, discussed above in relation to FIG. 1. The message flows 300 depicted in FIG. 3 are carried out such that the data processing system 105 (and in particular the link generation component 120) can facilitate the establishment of communication between the client computing device 150 and the service provider device 160 in instances where the lack of an identifier associated with the client computing device 150 may prevent the establishment of such communication. Further the message flows 300 are carried out to improve the reliability and efficiency of data transmission between the data processing system 105 and the service provider device 160, while also reducing resource consumption (e.g., bandwidth) by passing virtual identifiers and avoiding multiple queries and communications between the service provider device 160 and the client computing device 150 to enable the service provider device 160 to provide a requested service.

As discussed above, the data processing system 105 can receive a communication C1 from the client computing device 150, where the communication C1 can include an audio signal that includes a voice command from a user associated with the client computing device 150. The data processing system 105, and in particular the NLP component 110, can process the audio signal and identify a request and a keyword. For example, as discussed above the audio signal can include a message such as “OK, I would like to go to go dinner and then a movie tonight.” The data processing system can process the audio signals and detect at least one request indicating an interest to attend dinner and a movie, and at least one trigger keyword, e.g., “go” indicating a need for transportation. In response to determining the keyword is associated with transportation, the content selector component 125 can select a ride service that can be offered as an alternative to the default or preferred ride service associated with the client computing device 150. The data processing system 105 can generate an audio signal that includes a message presenting the content item to the user. For example, the audio file can include a message such as “Would you like to consider an alternative ride service PQR which is $5 cheaper than the XYZ ride service?” where “PQR” can stand for a name or moniker of the alternative ride service. The data processing system 105 sends a communication C2 that includes this audio file associated with the content item, as shown in FIG. 3.

The client computing device 150 can send a communication C3 in response to the communication C2, where C3 includes an audio signal that represents a response from a user. For example, the audio signal can include a response such as: “OK, I would like to use PQR” From this information the NLP component 110 (FIG. 1) identifies at least one request or at least one trigger keyword. For example, the NPL component 110 can identify a request for transportation, and a keyword “PQR” indicating the that the alternative ride service PQR has been requested.

Once the data processing system 105 identifies that the client computing device 150 is requesting the alternative content item, the link generation component 120 (FIG. 1) determines the service provider device 160 associated with the requested content item. The link generation component determines whether the data repository 145 (FIG. 1) includes any identifiers associated with the requested content item and the client computing device 150. If no identifier are found, the link generation component 120 sends a communication C4 to the service provider device 160 to determine the presence of a database record associated with the client computing device 150. The communication C4 can include an identity of the client computing device 150, or an identity of a user associated with the client computing device 150. The link generation component 120 can send the communication C4 to the service provider device 160 without querying the data repository 145 (FIG. 1).

The service provider device 160, in response to receiving the query for database records associated with the client identity in the communication C4, can send a communication C5 to the client database 164 to determine whether a database record associated with the client identity is present in the client database 164. If the client database 164 does not include any records associate with the client identity received in the communication C5, the client database 164 can return a communication C6 indicating that no such record exists. The service provider device 160 can, send a communication C7 to the data processing system 105 indicating that no database record associated with the client identity included in the communication C4 exists in the client database 164. The data processing system 105 can directly query the client database 164 with a communication C4′(Client identity) (shown in dotted lines in FIG. 3), to determine whether any records associated with the client identity are present in the client database 164. If no record are found, the client database 164 can return a communication C6′ with a Null response indicating the absence of the queried records. In some cases, the data processing system can determine the absence based on Null respond or other indication, response, character, symbol, string, alphanumeric character, or value that indicates an absence.

The service provider device 160 may be unable to provide the requested service to the client computing device 150, because there are no records associated with the client computing device 150 present in the client database 164. However, the data processing system 105 can mitigate the risk of lack of communication due to the lack of database records. In particular, the data processing system 105 generates a virtual identifier associated with the client computing device 150, and sends a communication C8 to the service provider device 160 to create a database record associated with the virtual identifier in the client database 164. As discussed above, the virtual identifier can include a combination of various data associated with the client computing device 150. For example, the virtual identifier can include a hash function of one or more of a device ID (such as a MAC ID of the client computing device 150), an Internet Protocol (IP) address of the client computing device 150, name of a user associated with the client computing device 150, a telephone number of the user, and any other data associated with the client computing device 150. The virtual identifier can include a digital certificate or a public key of the client computing device 150. The communication C8 also can include additional information associated with the client computing device 150 that can facilitate the establishment of communications between the service provider device 160 and the client computing device 150, or facilitate the provision of the requested service by the service provider device 160. The data processing system 105 can send the virtual identifier and the additional information formatted in a data structure such as the first, second, or the third data structures 200, 202, or 204 shown in FIGS. 2A-2C. The virtual identifier and the additional information can be communicated to the service provider device 160 (FIG. 1) using data packets (for example, in a payload section of the data packets) via the interface 115 (FIG. 1) and over the network 165 (FIG. 1).

The service provider device 160, upon receiving the communication C8, can create a database record based at least on the virtual identifier by sending a communication C9 to the client database 164. The communication C9 also can include the additional information received in the communication C8. After creating the database record associated with the virtual identifier, the client database 164 can send a communication C10 to the service provider device 160, indicating that the database record has been created. The service provider device 160, can send a communication C11 to the data processing system 105 indicating that the database record was successfully created.

Once the record associated with the client computing device 150 has been created in the client database 164, the service provider device 160 can communicate with the client computing device 150 to provide the service requested in the communication C3. For example the service provider device 160 can send a communication C12 to the client computing device 150 to confirm that the request for the alternate ride has been successful, or to acquire additional information from the client computing device 150 in relation to the requested service.

As discussed above, the data processing system 105 facilitates in establishing communication between the service provider device 160 and the client computing device 150 in instances where the lack of a database record associated with the client computing device 150. This avoids a situation where the request made by the client computing device would be otherwise stalled.

FIG. 4 depicts a method 400 to invoke actions for mitigating stalling of communication between a client computing device and a service provider device in a voice activated data packet based computer network environment such as the system 100. The method 400 depicted in FIG. 4 allows the data processing system 105 (e.g., via the link generation component 120) to facilitate the establishment of communication between the client computing device 150 and the service provider device 160 in instances where the lack of an identifier associated with the client computing device 150 may prevent the establishment of such communication. Further the method 400 improves the reliability and efficiency of data transmission between the data processing system 105 and the service provider device 160, while also reducing resource consumption (e.g., bandwidth) by passing virtual identifiers and avoiding multiple queries and communications between the service provider device 160 and the client computing device 150 to enable the service provider device 160 to provide a requested service.

The method 400 can receive data packets rom a client computing device (ACT 405). For example, the data processing system 105 can execute, launch or invoke the NLP component 110 to receive packet or other protocol based transmissions via the network 165 from the client computing device 150. The data packets can include or correspond to an input audio signal detected by the sensor 151, such as an end user saying “OK, I would like to go to go dinner and then a movie tonight” into a smartphone. Another example of this method step has been discussed above in relation to FIG. 3, where the communication C1, which includes a voice command from a user associated with the client computing device 150, is received by the data processing system 105.

The method 400 can identify at least one request or at least one trigger keyword from the input audio signal (ACT 410). For example, the NLP component 110 can parse the input audio signal to identify requests (“dinner” or “movie”) as well as trigger keywords “go” “go to” or “to go to” that correspond or relate to the request. The data processing system 105 can determine actions associated with the keyword, such as an action related to providing transportation to the user.

The method 400 can select a content item based on the keyword identified by the data processing system (ACT 415). For example, the content selector component 125, based on the identified requests and keywords, can select at least one content item. The data processing system 105 can select at least one output audio signal associated with the selected content item. For example, the content selector component 125 can select an output audio signal corresponding to an alternate ride sharing service. Another example of selecting a content item has been discussed above in relation to FIG. 3, where the data processing system 105 selects an output audio signal saying: “Would you like to consider an alternative ride service PQR which is $5 cheaper than the XYZ ride service?” where “PQR” can stand for a name or moniker of the alternative ride service. The data processing system 105 sends a communication C2 that includes this audio file associated with the content item, as shown in FIG. 3.

The method 400 includes determining an absence of a database record associated with the client computing device 150 (ACT 420). For example, the link generation component 120 can query (communication C4, FIG. 3) the service provider device 160 to determine whether a database record associated with the client computing device 150 is present in the client database 164 of the service provider device 160. Alternatively, as shown in FIG. 3, the data processing system 105 can directly query (communication C4′, FIG. 3) the client database 164 to determine the presence of records associated with the client computing device 150. The data processing system 105 can also query the data repository 145 to determine whether any of the identifiers 147 include an identifier associated with the client computing device 150 and the content item requested. If no record for an identifier associated with the client computing device 150 is present, the client database 164 can return a NULL response (communication C6 and C6′, FIG. 3), indicating as much.

The method 400 includes generating a virtual identifier (ACT 425). As discussed above, the link generation component 120 can generate a virtual identifier associated with the client computing device 150. The virtual identifier can be a unique identifier that identifies the client computing device 150. The virtual identifier can be a randomly generated number. The virtual identifier also can be determined using a hash function or a cryptographic function on data associated with the client computing device 150. Further, the virtual identifier can include a digital certificate or a public key that can be used for secure communication using a PKI.

The method 400 also includes sending the virtual identifier to the service provider device (ACT 430). As discussed above in relation to FIGS. 1-3, the link generation component 120 can send the virtual identifier associated with the client computing device to the service provider device 160 (communication C8, FIG. 3). The virtual identifier can be communicated to the service provider device 160 using data packets (for example, in a payload section of the data packets) via the interface 115 and over the network 165. The service provider device 160, creates a database record associated with the virtual identifier in the client database 164. Creating the record in the client database 164 can include creating an account for the client computing device 150 to enable the service provider device 160 to provide the requested service to the client computing device 150. The link generation component 120 can also store the virtual identifier as one of the identifiers 147 in the data repository 145. In one example, the link generation component 120 can send additional information to the service provider device 160. For example, the link generation component 120 can send information associated with the client computing device 150. Also, the link generation component 120 can poll for data from one or more sensors on the client computing device 150, and send the data along with the virtual identifier.

The method 400 includes receiving a communication of creation of a record (ACT 435). For example, as shown in FIG. 3, the data processing system 105 receives a communication C11 indicating that a record in the client database 164 has been created. After receiving the record creation communication, the data processing system 105 can wait to receive additional requests from the client computing device 150, or request for additional data from the service provider device 160.

FIG. 5 is a block diagram of an example computer system 500. The computer system or computing device 500 can include or be used to implement the system 100, or its components such as the data processing system 105. The data processing system 105 can include an intelligent personal assistant or voice-based digital assistant. The computing system 500 includes a bus 505 or other communication component for communicating information and a processor 510 or processing circuit coupled to the bus 505 for processing information. The computing system 500 can also include one or more processors 510 or processing circuits coupled to the bus for processing information. The computing system 500 also includes main memory 515, such as a random access memory (RAM) or other dynamic storage device, coupled to the bus 505 for storing information, and instructions to be executed by the processor 510. The main memory 515 can be or include the data repository 145. The main memory 515 can also be used for storing position information, temporary variables, or other intermediate information during execution of instructions by the processor 510. The computing system 500 can further include a read only memory (ROM) 520 or other static storage device coupled to the bus 505 for storing static information and instructions for the processor 510. A storage device 525, such as a solid state device, magnetic disk or optical disk, can be coupled to the bus 505 to persistently store information and instructions. The storage device 525 can include or be part of the data repository 145.

The computing system 500 can be coupled via the bus 505 to a display 535, such as a liquid crystal display, or active matrix display, for displaying information to a user. An input device 530, such as a keyboard including alphanumeric and other keys, can be coupled to the bus 505 for communicating information and command selections to the processor 510. The input device 530 can include a touch screen display 535. The input device 530 can also include a cursor control, such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor 510 and for controlling cursor movement on the display 535. The display 535 can be part of the data processing system 105, the client computing device 150 or other component of FIG. 1, for example.

The processes, systems and methods described herein can be implemented by the computing system 500 in response to the processor 510 executing an arrangement of instructions contained in main memory 515. Such instructions can be read into main memory 515 from another computer-readable medium, such as the storage device 525. Execution of the arrangement of instructions contained in main memory 515 causes the computing system 500 to perform the illustrative processes described herein. One or more processors in a multi-processing arrangement can also be employed to execute the instructions contained in main memory 515. Hard-wired circuitry can be used in place of or in combination with software instructions together with the systems and methods described herein. Systems and methods described herein are not limited to any specific combination of hardware circuitry and software.

Although an example computing system has been described in FIG. 5, the subject matter including the operations described in this specification can be implemented in other types of digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them.

For situations in which the systems discussed herein collect personal information about users, or may make use of personal information, the users may be provided with an opportunity to control whether programs or features that may collect personal information (e.g., information about a user's social network, social actions or activities, a user's preferences, or a user's location), or to control whether or how to receive content from a content server or other data processing system that may be more relevant to the user. In addition, certain data may be anonymized in one or more ways before it is stored or used, so that personally identifiable information is removed when generating parameters. For example, a user's identity may be anonymized so that no personally identifiable information can be determined for the user, or a user's geographic location may be generalized where location information is obtained (such as to a city, postal code, or state level), so that a particular location of a user cannot be determined. Thus, the user may have control over how information is collected about him or her and used by the content server.

The subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. The subject matter described in this specification can be implemented as one or more computer programs, e.g., one or more circuits of computer program instructions, encoded on one or more computer storage media for execution by, or to control the operation of, data processing apparatuses. Alternatively or in addition, the program instructions can be encoded on an artificially generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. A computer storage medium can be, or be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. While a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination of computer program instructions encoded in an artificially generated propagated signal. The computer storage medium can also be, or be included in, one or more separate components or media (e.g., multiple CDs, disks, or other storage devices). The operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.

The terms “data processing system” “computing device” “component” or “data processing apparatus” encompass various apparatuses, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, or combinations of the foregoing. The apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit). The apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them. The apparatus and execution environment can realize various different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures. The direct action API 135, content selector component 125, link generation component 120 or NLP component 110 and other data processing system 105 components can include or share one or more data processing apparatuses, systems, computing devices, or processors.

A computer program (also known as a program, software, software application, app, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program can correspond to a file in a file system. A computer program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs (e.g., components of the data processing system 105) to perform actions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatuses can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

The subject matter described herein can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a web browser through which a user can interact with an implementation of the subject matter described in this specification, or a combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), an inter-network (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).

The computing system such as system 100 or system 500 can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network (e.g., the network 165). The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some implementations, a server transmits data (e.g., data packets representing a content item) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., a result of the user interaction) can be received from the client device at the server (e.g., received by the data processing system 105 from the client computing device 150 or the content provider computing device 155 or the service provider device 160).

While operations are depicted in the drawings in a particular order, such operations are not required to be performed in the particular order shown or in sequential order, and all illustrated operations are not required to be performed. Actions described herein can be performed in a different order.

The separation of various system components does not require separation in all implementations, and the described program components can be included in a single hardware or software product. For example, the NLP component 110, the content selector component 125, or the link generation component 120 can be a single component, app, or program, or a logic device having one or more processing circuits, or part of one or more servers of the data processing system 105.

Having now described some illustrative implementations, it is apparent that the foregoing is illustrative and not limiting, having been presented by way of example. In particular, although many of the examples presented herein involve specific combinations of method acts or system elements, those acts and those elements may be combined in other ways to accomplish the same objectives. Acts, elements and features discussed in connection with one implementation are not intended to be excluded from a similar role in other implementations or implementations.

The phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of “including” “comprising” “having” “containing” “involving” “characterized by” “characterized in that” and variations thereof herein, is meant to encompass the items listed thereafter, equivalents thereof, and additional items, as well as alternate implementations consisting of the items listed thereafter exclusively. In one implementation, the systems and methods described herein consist of one, each combination of more than one, or all of the described elements, acts, or components.

Any references to implementations or elements or acts of the systems and methods herein referred to in the singular may also embrace implementations including a plurality of these elements, and any references in plural to any implementation or element or act herein may also embrace implementations including only a single element. References in the singular or plural form are not intended to limit the presently disclosed systems or methods, their components, acts, or elements to single or plural configurations. References to any act or element being based on any information, act or element may include implementations where the act or element is based at least in part on any information, act, or element.

Any implementation disclosed herein may be combined with any other implementation or embodiment, and references to “an implementation,” “some implementations,” “one implementation” or the like are not necessarily mutually exclusive and are intended to indicate that a particular feature, structure, or characteristic described in connection with the implementation may be included in at least one implementation or embodiment. Such terms as used herein are not necessarily all referring to the same implementation. Any implementation may be combined with any other implementation, inclusively or exclusively, in any manner consistent with the aspects and implementations disclosed herein.

References to “or” may be construed as inclusive so that any terms described using “or” may indicate any of a single, more than one, and all of the described terms. For example, a reference to “at least one of ‘A’ and ‘B’” can include only ‘A’, only ‘B’, as well as both ‘A’ and ‘B’. Such references used in conjunction with “comprising” or other open terminology can include additional items.

Where technical features in the drawings, detailed description or any claim are followed by reference signs, the reference signs have been included to increase the intelligibility of the drawings, detailed description, and claims. Accordingly, neither the reference signs nor their absence have any limiting effect on the scope of any claim elements.

The foregoing implementations are illustrative rather than limiting of the described systems and methods. Scope of the systems and methods described herein is thus indicated by the appended claims, rather than the foregoing description, and changes that come within the meaning and range of equivalency of the claims are embraced therein.

What is claimed is: 

1. A system to provide identifier dependent operation processing of packet based data communication between a client computing device and a service provider device, comprising: a natural language processor component executed by a data processing system to receive, via an interface of the data processing system, data packets comprising an input audio signal detected by a sensor of a client computing device having a device identifier; the natural language processor component to parse the input audio signal to identify a request and a trigger keyword corresponding to the request; a content selector component executed by the data processing system to receive the trigger keyword identified by the natural language processor and to select, based on the trigger keyword, a content item via a real-time content selection process; a link generation component to: perform a lookup of a device identifier of the client computing device in a database storing account identifiers established for a service provider device corresponding to the content item; determine an absence of the device identifier of the client computing device in the database based on a null command received in response to the lookup; generate, a virtual identifier for the client device and link the virtual identifier to the device identifier; and route data packets that carry, in a payload section, the virtual identifier to service provider device to cause the service provider device to establish an account for the client computing device based on the virtual identifier; and the data processing system to receive, from the service provider device, an indication that the service provider device established the account using the virtual identifier, and performed an operation with the client computing device.
 2. The system of claim 1, comprising: the link generation component to send client computing device information to the service provider device, wherein the client computing device information is distinct from the device identifier.
 3. The system of claim 2, comprising: the link generation component to communicate with the client computing device to obtain client computing device information.
 4. The system of claim 2, comprising: the link generation component to communicate with the client computing device to obtain client computing device information based on data from one or more sensors included in the client computing device.
 5. The system of claim 2, comprising: the link generation component to generate a data structure including the client computing device information, and to route the data packets that carry, in the payload section, the data structure.
 6. The system of claim 1, comprising: the link generation component to send a time based validity information of the virtual identifier.
 7. The system of claim 6, comprising: the link generation component to instruct the service provider device to delete the account for the client computing device responsive to invalidation of the virtual identifier.
 8. The system of claim 1, wherein the lookup is carried out by the service provider device.
 9. The system of claim 1, comprising: the link generation component to carry out the lookup.
 10. The system of claim 1, comprising: the link generation component to generate the virtual identifier using at least one of a hash function and a cryptographic function.
 11. The system of claim 1, comprising: the link generation component to generate the virtual identifier including a digital certificate.
 12. A method to invoke actions for identifier dependent operation processing of packet based data communication between a client computing device and a service provider device using a data processing system, comprising: receiving, by a natural language processor component executed by the data processing system, from the client computing device, an audio signal corresponding to a voice command; processing, by the natural language processor component, the audio signal to identify a request for a service and a trigger keyword corresponding to the request; selecting, by a content selector component executed by the data processing system, based on the keyword, a content item corresponding to the service provider device communicably coupled to the data processing system; determining, by a link generation component executed by the data processing system, an absence of a database record corresponding to a client computing device identifier associated with the client computing device in a database associated with the service provider device; generating, by the link generation component responsive to determining the absence, a virtual identifier associated with the client computing device, the virtual identifier being distinct from the client computing device identifier; sending, by the link generation component, the virtual identifier to the service provider device; and receiving, by the link generation component, a first message from the service provider device indicating establishment of a database record corresponding to the virtual identifier.
 13. The method of claim 12, further comprising: sending, by the link generation component responsive to determining the absence, client computing device information to the service provider device, wherein the client computing device information is distinct from the client computing device identifier.
 14. The method of claim 13, comprising: communicating, by the link generation component, with the client computing device to obtain client computing device information, wherein sending client computing device information to the service provider device comprises sending the client computing device information obtained from the client computing device.
 15. The method of claim 13, comprising: communicating, by the link generation component, with the client computing device to obtain client computing device information based on data from one or more sensors included in the client computing device.
 16. The method of claim 13, comprising: generating, by the link generation component, a data structure including the client computing device information, wherein sending, by the link generation component, the client computing device information to the service provider device comprises sending the data structure to the service provider device.
 17. The method of claim 13, comprising: sending, by the link generation component, instructions to the service provider device to create the database record corresponding to the virtual identifier.
 18. The method of claim 17, wherein sending, by the link generation component, instructions to the service provider device to create the database record corresponding to the virtual identifier comprises sending time based validity information of the virtual identifier.
 19. The method of claim 18, comprising: sending, by the link generation component, responsive to a determination that the virtual identifier is no longer valid, instructions to the service provider device to delete the database record corresponding to the virtual identifier.
 20. The method of claim 12, comprising: generating, the virtual identifier associated with the client computing device using at least one of a hash function and a cryptographic function. 